Configuring the Storage Service

Storage Service (an option on the AssetWise Server installer) is used to manage AssetWise storage devices and repositories.

A device or storage device specifies the root folder on a file storage server under which one or more repositories reside. For example: C:\ebstorage
A repository is the folder under a device where the files that get added to the AssetWise community are stored.

The computer where the physical repository resides does not require that you install any AssetWise software on it. Therefore you can set up a repository on the local AssetWise Server, on a remote Storage Service, or on a remote server with no AssetWise software installed at all.

In AssetWise System Management Console, the Storage node is where you define and manage the storage devices and repositories of a particular AssetWise server. The Storage node is only present under a particular server node when the Storage Service is installed on that server computer. When you select the Storage node, the content pane is split into two sections:

The upper section lists the storage devices managed by the Storage Service on this AssetWise server.
The lower section lists the available communities of this AssetWise server, letting you select which communities you want this Storage Service to serve.

When creating a device that points to a local folder, you can specify either a logical path or a UNC path. When creating a device that points to a folder on a remote file storage server, you must use a UNC path. Examples:

C:\ebstorage (logical device)

\\servername\ebstorage (UNC device)

When creating a device using a logical path, you do not need to manually create the device folder. AssetWise will create it as needed (along with the repository folder) the next time a file is added to the community and placed into the device's repository. When creating a device using a UNC path, you must manually create the device folder, share it, and give access (Full Control) to the service identity used by the Storage Service, before it can be used. When using a UNC path, AssetWise will create the repository folder as needed.

AssetWise System Management Console provides two methods for creating storage devices and repositories. You can either use the Device Properties and Repository Properties dialogs to create a storage device and repository, or you can use the Storage Wizard to create both the storage device and the repository (and optionally the community) in one process. You can also use the Storage Wizard to move a repository another storage server, or to another location on the same storage server.

To Enable the Storage Service for Your Community

In the Explorer pane, expand Servers > your_server.
Select the Storage node.
In the Communities Served list, check the check box next to your community.
Log in to the community if prompted.

The Storage Service running on this computer is now configured to serve the selected community.
If you want to use more than one Storage Service for a single community, repeat these steps for each installation of Storage Service so that all instances of Storage Service are enabled for your community.

To Create a Storage Device

This task requires that you have already created a community. See To Create a Community .

In the Explorer pane, expand Servers > your_server.
Right-click the Storage node and select Add Device.
The New Device Properties dialog opens.
In the Name field: Enter a name for the storage device.
(Optional) In the Description field: Enter a description for the storage device.
From the Driver list: Select which file driver this storage device will use.
See Storage Device File Drivers .
Configure additional parameters depending on the driver selected.
From the Speed list: Select a response time for the selected driver.
For example, optical is considered slow and local magnetic disks are considered fast.
In the Root Access field: Enter the path to the root folder on the file storage server under which your repository will reside.
The root folder can be a folder on the local computer or on a remote computer. If the folder is local, the format can be a logical path (for example, C:\awstorage) or a UNC path (for example, \\servername\awstorage). If the folder is on a remote computer, you must use a UNC path. When using a logical path, you do not need to manually create the device folder; AssetWise will create it (and the repository folder) as needed, the next time a file is added to the community and placed into the device's repository. When using a UNC path, you must manually create the device folder, share it, and give access (Full Control) to the service identity used by the Storage Service. In this case, AssetWise will create just the repository folder as needed.
Click OK.

Multiple storage areas can be set up on the AssetWise Information Integrity Server, as the AssetWise Information Integrity Server has the ability to host more than one community. To apply the storage area to a specific community, it is necessary to check the check box next to the correct community.

There is a location on the AssetWise Installation Worksheet to store this information.

After you create a storage device, the next step is to create and assign one or more repositories to this storage device. These repositories are basically subdirectories created under the Root Access storage directory. When objects are added into AssetWise, they can be directed to certain repositories if desired, to keep groupings of like documents physically isolated. This may be a requirement in an environment where records management is a goal.

To Create a Repository

In the Explorer pane, expand Servers > your_server > Storage.
Right-click the storage device under which you want to create a repository and select Add Repository.
The New Repository Properties dialog opens.
In the Name field: Enter a logical name for the repository.
Repository names must be unique within a community.
From the Community list: Select the community you want this repository to serve.
In the Path field: Enter the name for the physical repository folder that will be created under the device.
The name you enter in the Path field is automatically appended to the Full Path field, which includes the device and displays the full path to the physical repository folder. For example:

C:\awstorage\repository

or

\\servername\awstorage\repository

There is no need to manually create the physical repository folder. AssetWise will create it as needed, the next time a file is added to the community and placed into this repository.

Note: The service identity of the Storage Service must have at least Modify permissions on the repository folder.
Assuming this is a normal AssetWise repository, leave the default options as they are.

See Repository Options for descriptions.
Click OK.

The Select Repository Group dialog opens.

Tip: If you need to create a new repository group in the selected community, you can do so from this dialog by clicking the Add Group button.
Select which repository group in the selected community you want this new repository to belong to and click OK.
The repository is added under the selected storage device under the Storage node.

To Create a Community, Storage Device, and Repository Using the Storage Wizard

This task requires that you have already created a datasource (see To Create a Datasource ).

The Storage Wizard lets you create a community, a storage device, and a repository all in one process. For each item, the wizard will prompt you to either create a new one or select an existing one. For the sake of simplicity this procedure assumes that you are creating new items.

Open AssetWise System Management Console (Start > Bentley > eB System Management Console).
In the Explorer pane, expand Servers > your_server.
Right-click the Storage node and select Storage Wizard.

The Storage Wizard opens.
On the Welcome page:
1. Select Add a new Repository.
2. Click Next.
On the Select the Community page:
1. Select Create a new community.
2. Click Next.
On the New Community page:
1. In the Application Server Name field: Enter the name of the AssetWise Information Integrity Server computer.
  (The local computer name is listed by default. If this is the computer you want to use, leave it as is.)
2. Click Next.
On the Select Datasource page:
1. Select a datasource from the Data Source list.
  (This list displays the datasources that exist on the AssetWise Information Integrity Server selected on the previous page.)
2. Click Next.
On the Login page:
1. In the Username and Password fields: Enter the credentials of the default AssetWise administrator account for the community.
2. Click Next.
Important: After you finish working in AssetWise System Management Console, you are prompted with a dialog asking to change the ADMIN user password and blocking other steps until the password is changed. Account passwords are changed in AssetWise Director.
On the Select a Device page:
1. Select Create a new Device.
2. Click Next.
On the Create a New Device page:
1. In the Device Name field: Enter a name for the storage device.
2. Click Next.
On the Device Properties page:
1. From the Device Type list: Select which file driver this storage device will use.
  
  See Storage Device File Drivers .
2. Configure additional parameters depending on the driver selected.
3. In the Root Access for the Device field: Enter the path to the root folder on the file storage server under which your repository will reside.
  
  The root folder can be a folder on the local computer or on a remote computer. If the folder is local, the format can be a logical path (for example, C:\awstorage) or a UNC path (for example, \\servername\awstorage). If the folder is on a remote computer, you must use a UNC path. When using a logical path, you do not need to manually create the device folder; AssetWise will create it (and the repository folder) as needed, the next time a file is added to the community and placed into the device's repository. When using a UNC path, you must manually create the device folder, share it, and give access (Full Control) to the service identity used by the Storage Service. In this case, AssetWise will create just the repository folder as needed.
4. Click Next.
On the Create a New Repository page:
1. In the Repository Name field: Enter a logical name for the repository.
  
  Repository names must be unique within a community.
2. Click Next.
On the Repository Location page:
1. In the Repository Location Relative to Device Location field: Enter the name for the physical repository folder that will be created under the device.
  
  The folder name you enter is automatically appended to the read-only field below it, which includes the device and displays the full path to the physical repository folder. For example:
  
  C:\awstorage\repository
  
  or
  
  \\servername\awstorage\repository
  
  There is no need to manually create the physical repository folder. AssetWise will create it as needed, the next time a file is added to the community and placed into this repository.
  
  Note: The service identity of the Storage Service must have at least Modify permissions on the repository folder.
2. Assuming this is a normal AssetWise repository, leave the default options as they are.
  
  See Repository Options for descriptions.
3. Click Next.
On the New Repository Settings page:
1. Assuming this is a normal AssetWise repository, leave the default options as they are.
  
  See Repository Options for descriptions.
2. Click Next.
On the Repository Group page:
1. Select Use an existing Group.
2. Select a group from the list.
3. Click Next.
On the Ready to Create the Repository page, review your settings and click Finish.
On the Finished page, click Close.

Storage Device File Drivers

AssetWise delivers the following file drivers to choose from when creating a storage device.

Driver	Description
eB File Driver	Used to connect to other AssetWise communities so external file links can be made to another system. Additional parameters you need to set for this driver: Server DataSource Username Password
FTP File Driver	Used if the mechanism for copying files between the AssetWise Information Integrity Server and repository is to be FTP (File Transfer Protocol). This is a common configuration if the repository resides on a non-Windows computer (such as UNIX). Additional parameters you need to set for this driver: FTP Server User ID Password Port
HTTP File Driver	Used if the mechanism for copying files between the AssetWise Information Integrity Server and repository is to be HTTP (Hypertext Transfer Protocol). Additional parameters you need to set for this driver: Username Password
Windows File Driver	Used if the storage device points to a logical drive whereby normal Windows read/writes are processed. Select this driver when creating a dedicated device for an FTR repository. This driver has no additional configuration parameters.
Windows File Driver with Secure Delete	Used if the storage device points to a logical drive whereby normal Windows read/writes are processed. Deleted files will have their data overwritten to prevent recovery by any file recovery software. This driver has no additional configuration parameters.
Microsoft Windows Azure Storage Driver	Intended for use in situations where AssetWise servers are hosted in the cloud (for example, as part of aBentley MANAGEservices implementation). Additional parameters you need to set for this driver: StorageAccount AccountKey
ProjectWise File Driver	Used to connect AssetWise communities to ProjectWise datasources, sync, exchange data files between it. Additional parameters you need to set for this driver: Server DataSource Username Password

Repository Options

These options are available when you view the properties of an existing repository.

Default options are selected when you create the repository, whether using the New Repository Properties dialog or the Storage Wizard.

Setting	Description
Write Enabled	When on (the default), users can edit the contents of files in the repository. Only turn this option off if you do not want users to be able to edit files in this repository (the files will be read-only).
Delete Enabled	When on (the default), users can delete files from the repository. Only turn this option off if you do not want users to be able to delete files from this repository.
External Repository	This option is off by default. Only turn it on if this repository resides physically external to AssetWise and is accessed via a pointer, or link, to a non- AssetWise repository (for example, COLD).
Used for Full Text Retrieval	This option is off by default. Only turn it on if this repository is to be used for full text retrieval (FTR). When files in your community are submitted for FTR indexing, they are copied from their original repository to a dedicated FTR repository where they can be processed. You must create an FTR repository if want to use the full text retrieval feature of AssetWise. There can only be one FTR repository per community, and turning this option on is what makes it an FTR repository. Turning this option on automatically sets the name of the repository to "FTR" and disables the other options. The Path field lets you enter a name of the physical repository folder that will be created and used for FTR. The path to the FTR repository must be accessible with read permissions as a UNC drive from the database server. In the Storage Wizard, this option is labeled Repository will be Used for Full Text Retrieval.
Create Signatures	When on (the default), a signature is created for each file added to the repository. In the Storage Wizard, this option is labeled Create File Signatures. It is recommended that you leave this setting on. A repository cannot be a replication source if the files they contain do not have signatures created for them.
Verify Signatures	When on (the default), a file in this repository will be checked for a valid signature any time the file is read (for example, when the file is downloaded, or replicated). In the Storage Wizard, this option is labeled Verify File Signatures during read operations. It is recommended that you leave this setting on.
Replication Source	When on (the default), then the files of this repository can be replicated in other repositories (those repositories who have the Replication Destination option turned on). Only turn this option off if you do not want the files of this repository to be replicated in other repositories.
Replication Destination	When on (the default), then this repository can receive files replicated from other repositories (those repositories who have the Replication Source option turned on). Only turn this option off if you do not want this repository to receive files replicated from other repositories.
Take this Repository Offline	When off (the default), this repository is available for use. Turn this option on if you need to make the repository unavailable for use (for example, if you need to do maintenance on the server hosting the repository).

To Move a Repository Using the Storage Wizard

You can use the Storage Wizard to help you move a repository from one storage server to another, or to another device on the same storage server. First you copy or move the physical repository folder to its new location, then you use the Storage Wizard to reconnect the community to the repository in its new location.

Copy or move the physical repository folder from the old device folder to the new device folder.
For example, from C:\olddevice\mainrepo to D:\newdevice\mainrepo.

The new device folder can be on the same computer as the old device folder, or on another computer.

Note: If you want or need to specify a UNC path (\\servername\newdevice) when creating the device in AssetWise System Management Console, you also need to share the new device folder, and give access (Full Control) to the service identity used by the Storage Service, in order for it to be used.
Open AssetWise System Management Console (Start > Bentley > eB System Management Console).
In the Explorer pane, expand Servers > your_server.
Right-click the Storage node and select Storage Wizard.

The Storage Wizard opens.
On the Welcome page:
1. Select Move a repository.
2. Click Next.
On the Select Community page:
1. From the Available Communities list: Select the community that owns the repository you are moving.
2. Click Next.
On the Login page:
1. In the Username and Password fields: Enter the credentials of the default AssetWise administrator account for the community.
2. Click Next.
On the Browse for Repository page:
1. From the Repository list: Select the repository that you want to move.
2. Click Next.
On the Select a Device page:
1. Select Create a new Device.
2. Click Next.
On the Create a New Device page:
1. In the Device Name field: Enter a name for the storage device.
2. Click Next.
On the Device Properties page:
1. From the Device Type list: Select which file driver this storage device will use.
  
  See Storage Device File Drivers .
2. Configure additional parameters depending on the driver selected.
3. In the Root Access for the Device field: Enter the path to the new device folder you created in step 1.
  If the new device folder is a local folder, the format can be a logical path (C:\newdevice) or a UNC path (\\servername\newdevice). If the new device folder is on a remote computer, you must use a UNC path.
4. Click Next.
On the Repository Location page:
1. In the Repository Location Relative to Device Location field: This field is already populated with the name of the repository folder that you copied or moved in step 1. Leave it as is.
  The read-only path field below it includes the new device and displays the full path to the physical repository folder. For example:
  
  C:\newdevice\mainrepo
  
  or
  
  \\servername\newdevice\mainrepo
  
  Note: The service identity of the Storage Service must have at least Modify permissions on the repository folder.
2. Click Next.
On the Ready to Move the Repository page, review your settings and click Finish.
On the Finished page, click Close.

Under the Storage node, you can click the old and new devices, and see that the repository has been moved from the old device to the new device.

You may need to refresh or possibly restart the Storage Service to see the change.

Old device, existing repository is no longer there:

New device, existing repository is now here:

To Set Up Multiple Storage Services to Serve the Same Repository

You can configure your system to have multiple storage services installed on multiple computers, all serving the same physical repository.

This is useful both for performance and for redundancy in case of failover. For example, you may find that a single storage server does not have enough processing power to handle all your storage work. Setting up additional storage servers spreads the work load between multiple servers for the same repository. Also, having multiple storage servers allows for redundancy in the event that one of the storage servers becomes unavailable.

The basic workflow is to create a storage device and repository for your community on one storage server as usual, then later you can set up additional storage servers and create a repository on each server that is linked to the original repository.

It is assumed that you have already created a storage device and repository for your community.
If it is not already shared, share the physical device folder and repository folder, and give access (Modify permission) to the service identity used by the Storage Service that you will install in the next step.
Use the AssetWise Information Integrity Server installer to install the Storage Service on another server.

Typically you can just install the full AssetWise Information Integrity Server (by default all options are on) and then disable the individual services you are not using in AssetWise System Management Console (under the Service Manager node). Another option is to install just the Application Server and Storage Service options in the AssetWise Information Integrity Server installer.
On the computer where you just installed the additional Storage Service, open AssetWise System Management Console (Start > Bentley > eB System Management Console)
Create a community that points to an existing datasource on the main AssetWise Server computer.
1. In the Explorer pane, expand Servers > your_server.
2. Right-click the Communities node and select Add Community.
3. In the Application Server field: Specify the name of the AssetWise Server computer that hosts the datasource.
4. From the Datasource list: Select your datasource.
5. Click OK.
6. Log in to the community when prompted using your default AssetWise admin account.
The community is created and added to the list of communities.
Enable the Storage Service for this new community.
1. Select the Storage node.
2. In the Communities Served list, check the check box next to your community.
Create a storage device and repository on this computer that is linked to the original storage device and repository using the Storage Wizard.
1. Right-click the Storage node and select Storage Wizard.
  
  The Storage Wizard opens.
2. On the Welcome page:
  1. Select Add a new Repository.
  2. Click Next.
3. On the Select the Community page:
  1. Select Use an existing Community.
  2. Select the community you created in step 5 from the list.
  3. Click Next.
4. On the Select a Device page:
  - Select Create a new Device.
  - Click Next.
5. On the Create a New Device page:
  1. In the Device Name field: Enter a name for the storage device.
    This name can be anything - it does not have to match the original device name.
  2. Click Next.
6. On the Device Properties page:
  1. From the Device Type list: Select the same driver used by the original storage device.
  2. In the Root Access for the Device field: Enter the path to the original storage device folder.
    The path you enter in the Root Access field here must match the path entered in the same field on the original storage device. The path is case sensitive, so if you do not enter it exactly the same, you will not be able to link the two repositories further down in this procedure.
  3. Click Next.
7. On the Create a New Repository page:
  1. In the Repository Name field: Enter anything for the repository name - it will automatically be changed to match the original repository name.
  2. Ignore the other settings - this linked repository will automatically inherit the settings of the original repository.
  3. Click Next.
8. On the Repository Location page:
  1. In the Repository Location Relative to Device Location field: Enter the name of the original repository folder that is located under the original device folder.
  2. Press the <Tab> key so that the field below it is updated to reflect the full path.
  3. Click Next.
9. On the New Repository Settings page, ignore these settings and click Next.
  This linked repository will automatically inherit the settings of the original repository.
10. When prompted, click Yes to link this new repository to the original repository.
11. On the Ready to Create the Repository page, review your settings and click Finish.
12. On the Finished page, click Close.
  
  The new device and repository are created on this server and are linked to the original device and repository on the original storage server.

The linked repository inherits the settings of the original repository. You can change the settings for the repository as usual, for example it can be taken offline, the Write Enabled setting be changed, the repository name may be changed, and so on. Because they are linked, you can change repository settings from the original repository or from the linked repository. Once the changes are made on one server, the other server will detect the change and automatically synchronize their local settings.

If you need to delete a linked repository, right-click the linked repository and select Delete Repository. When prompted, click Yes to confirm that you want to delete this repository. A second dialog opens, asking whether you want to delete the just linked repository, or if you want to delete the original repository as well. Click Yes to delete just the linked repository, click No to delete the original repository as well as all the linked repositories.